Access control for a document management and collaboration system

ABSTRACT

A method and apparatus for controlling access to documents retained by a document management and collaboration system is disclosed. The document management and collaboration system may generate one or more suggested privileges associated with one or more users. An access control policy may specify whether system-generated user privileges may be enforced. If they are enforced, access to one or more document may be made subject to the generated privileges.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.14/175,884, filed Feb. 7, 2014, entitled “ACCESS CONTROL FOR A DOCUMENTMANAGEMENT AND COLLABORATION SYSTEM,” the full disclosure of which isincorporated by reference for all purposes herein. This application alsoincorporates by reference for all purposes the full disclosures ofco-pending U.S. patent application Ser. No. 14/077,204, filed Nov. 11,2013, entitled “DOCUMENT MANAGEMENT AND COLLABORATION SYSTEM” andco-pending U.S. patent application Ser. No. 14/175,898, filed Feb. 7,2014, entitled “FORMING A DOCUMENT COLLECTION IN A DOCUMENT MANAGEMENTAND COLLABORATION SYSTEM.”

BACKGROUND

The use of remote computing services, such as remote document storage,has greatly increased in recent years. An organization, for example, maysupport its operations using both internal networks of computingresources and computing resources managed by others. Computers of theorganization, for instance, may communicate with computers of otherorganizations to access and/or provide documents or other data whileusing services of another organization. In many instances, organizationsconfigure and operate remote networks using hardware managed by otherorganizations, thereby reducing infrastructure costs and achieving otheradvantages. With such configurations of computing resources, ensuringthat access to the resources and the data they hold can be challenging,especially given the multitude of different computing systems. Forexample, computers of the organization may include Personal Computers,Tablets, Smartphones, Laptops and other devices.

It is often challenging to implement mechanisms that ensure thatdocuments are properly shared among users by providing users with anappropriate level of access to documents. Further, it is oftenchallenging to ensure that existing access privileges are examined inorder to improve security when documents are shared.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 shows an example of a document management and collaborationsystem configured to suggest access privileges in accordance with atleast one embodiment;

FIG. 2 shows an example of computing devices connected to a computingresource service provider in accordance with at least one embodiment;

FIG. 3 shows the functional entities of the front-end system and thedocument management and collaboration system in accordance with at leastone embodiment;

FIG. 4 shows an example of directory structure in accordance with atleast one embodiment;

FIG. 5 shows an example of a document management and collaborationsystem in accordance with at least one embodiment;

FIG. 6 shows an example of a method for evaluating an access requestbased at least in part on a requester's identity in accordance with atleast one embodiment;

FIG. 7 shows an environment for providing document sharing suggestionsin accordance with at least one embodiment;

FIG. 8 shows an example of a method for generating a similarity measurefor a document in accordance with at least one embodiment;

FIG. 9 shows an example of a method for recommending a change to accessprivileges in accordance with at least one embodiment; and

FIG. 10 illustrates an environment in which various embodiments can beimplemented.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. Forpurposes of explanation, specific configurations and details are setforth in order to provide a thorough understanding of the embodiments.However, it will also be apparent to one skilled in the art that theembodiments may be practiced without the specific details. Furthermore,well-known features may be omitted or simplified in order not to obscurethe embodiment being described.

Techniques described and suggested herein include controlling access toone or more documents retained by a document management andcollaboration system. The document management and collaboration systemmay store documents for an organization comprising a number of members(for example, administrators and users) and may facilitate sharing thedocuments between the members. Accordingly, more than one user canaccess a document. Further, the users may annotate the document, providefeedback on the document or otherwise comment on the document.

An administrator for an organization may be responsible for settingaccess privileges that are given to various users within theorganization. The administrator may specify an access control policythat dictates the access privileges given to users. Per the accessprivileges, the user may be permitted or denied from viewing a document,commenting on the document or expanding a sharing permission of thedocument to a member or a non-member of the organization or a registeredor non-registered users of the document management and collaborationsystem, among others.

The document management and collaboration system or another entity mayformulate access privileges for one or more users, and the formulatedaccess privileges may be suggested to the administrator for enforcementor for incorporation in an access control policy. The suggested accessprivileges may be based at least in part on attributes of users ordocuments. The attributes may be used to determine a user affinity for adocument or may be used to measure a significance of the document to auser. The attributes of users or documents may be received from one ormore services utilized by the users, such as an email service, acalendar service or a location service, among others. For example, anemail service may indicate that a user that uploaded a document alsosent the document to one or more other users. Accordingly, the documentmay be deemed as significant to the one or more other users and ameasure for affinity or significance of the document to the user may beupdated.

Further, one or more engines may be used for obtaining a user ordocument attribute, such as a cluster matching engine that correlates acharacter map (also referred to herein as a word cloud or a word map) ofcharacters that appear in the content of a document with a character mapof a user. The character map of the user may be constructed based atleast in part on the content of documents accessed by a user or uploadedby the user. Attributes received by the document management andcollaboration system or a measure of affinity obtained based at least inpart on the attributes may be used to suggest an access privilege forthe user.

The suggested access privileges may be made available to anadministrator (for example, by sending a notification to theadministrator or by storing the suggested access in a database or datastore accessible to the administrator), and, in turn, the administratormay provide an indication as to whether the suggested access privilegesare to be enforced for document access. In alternative embodiments, anaccess control policy may indicate that some (for example, accessprivileges below a certain level) or all suggested access privileges maybe enforced without prior acceptance by an administrator.

As described herein, an access control policy may specify that a user,without prior authorization from an administrator, may expand apermission associated with a document, for example, by sharing thedocument with a set of users and causing the set of users to have apermission to access the document. As described herein, a permission toaccess a document may be a privilege to view the document, modify thedocument, provide feedback on the document and/or annotate the document,among others. Modifying the document may include changing the content ofthe document or adding a new version of the document. After thepermission is granted, the user may be prompted to confirm that thepermission is to remain in force. Prompting the user may be performedbased at least in part on a trigger, periodically or according to a timeschedule. If the user does not confirm that the permissions are toremain in force, the permissions may be denied or some or all of the setof users may granted a permission level set by the access controlpolicy, whereby the permission level set by the policy may be lower thanthat presently provided to the set of users. Further, the policy mayspecify that the permission is to be set by the document management andcollaboration system based at least in part on a measure of affinity orsignificance. As described herein, setting or resetting a permission ofa set of users or soliciting a user to confirm an expanded permission isreferred to herein as baselining.

FIG. 1 shows an example of a document management and collaborationsystem configured to suggest access privileges in accordance with atleast one embodiment. The document management and collaboration system106 may manage a collection of documents for an organization and mayfacilitate access to the documents. Further, the document management andcollaboration system 106 may enforce access policies for the documents.As shown in FIG. 1, the document management and collaboration system 106receives an access control policy (for example, from an administrator ofthe organization) and uses the access control policy to govern access tothe documents. For example, based at least in part on the access controlpolicy the document management and collaboration system 106 may permitor deny user access to the document or restrict one or more actionstaken by the user with respect to a document of the organization.

In addition, the document management and collaboration system 106 mayformulate suggested access privileges for users. For example, thedocument management and collaboration system 106 may utilize document oruser attributes to recommend a privilege to be given to a user. The oneor more attributes may be received from a variety of services, such asan email service, a calendar service or a corporate directory. Forexample, the email service may indicate that a user that uploaded adocument has referenced the document in an email to one or more users.Accordingly, the indication may be used to determine whether the one ormore users are candidates for receiving access to the document. Inanother example, a calendar service may indicate that the one or moreusers are scheduled to meet with the user that uploaded the document fora specified period of time. Accordingly, the indication may be used todetermine whether the one or more users are to be given access to thedocument for the specified period of time. The document management andcollaboration system 106 may formulate a suggested access privilege 104for the one or more users and provide the suggested access privilege toan administrator or the user (for example, the user that uploaded thedocument). Further, a determination as to whether to enforce thesuggested access privilege 104 may be made by the administrator or theuser. In some embodiment, the access control policy may specify whetherthe suggested access privilege 104 may be enforced.

FIG. 2 shows an example of computing devices connected to a computingresource service provider in accordance with at least one embodiment.The computing devices 202 may be any device that is capable ofcommunicating with the computing resource service provider 210 or itsentities. The computing devices 202 may also be equipped with local orremote (for example, network-based) computational and storagecapabilities. The computational capabilities may be provided or enabledby a processor, such as a central processing unit (CPU), graphicsprocessing unit (GPU), digital signal processor and the like. Examplesof CPUs include CPUs that employ an x86 architecture (for example, asused in desktop and laptop computing devices) or a reduced instructionset computing (RISC) architecture (for example, as used in smartphoneand tablet computing devices). The computing devices 202 may also beequipped with communications and networking hardware and may be capableof communicating using any communications protocol. Further, thecomputing devices 202 may be equipped with input/output devices that mayinclude a display, a touch screen-based or keyboard-based input deviceor speakers. Additionally, the computing devices may include any type ofmemory, such as static or dynamic memory, and a power source or a poweradapter. Aside from their hardware capability, the computing devices 202may be configured to run or execute an operating system and/or otherprograms and the computing devices' 202 associated memory may storeexecutable instructions that, when executed by one or more processor,cause one or more functions to be performed or cause the operatingsystem and/or other programs to run. Although two devices are shown inFIG. 2, any number of devices may be contemplated in variousembodiments. Further, the computing devices 202 may communicate with thecomputing resource service provider 210 or any entity of the computingresource service provider 210 via a network (not shown). The network maybe public or private, whereby examples of the network include theInternet and an Internet service provider (ISP) network.

The computing devices 202 may collectively or individually be associatedwith a user or a customer of the computing resource service provider 210or its entities and functions. The user may be part of an organizationthat may utilize one or more of the services provided by the computingresource service provider 210 to maintain and deliver information to itsemployees, which may be located in various geographical locations.Additionally, the user may be an individual that utilizes the servicesof the computing resource service provider 210 to deliver content to aworking group located remotely. Further, one or more of the computingdevice 202 may belong to an administrator of an organization or a group.The administrator may utilize the computing device 202 to communicatewith the computing resource service provider 210 to specify accesscontrol policies. Utilizing a computing device, the administrator mayspecify permission levels of users.

The computing resource service provider 210 includes a front-end system204 and a file management and collaboration system 206 as well asplurality of services and systems as shown in FIG. 2. These include acontent distribution edge network 212, an object-level data storageservice 214, a virtual computing service 216, a task management andworkflow service 218, a managed directory service 222, a custom searchservice 224, a scalable database service 226 and a notification service228. It is noted that in various embodiments, the computing resourceservice provider 210 may include fewer services and systems than thosedescribed with references to FIG. 2 or may include additional oralternative services or systems to those described with reference toFIG. 2. Further, in alternative embodiments, the systems and servicesmay be utilized outside the context of the computing resources serviceprovider 210. For example, the services and systems may be stand-aloneor used in conjunction with systems and services other than thosedescribed with reference to FIG. 2.

The front-end system 204 may be a gateway to the file management andcollaboration system 206 and may offer private and public services tousers, administrators or their computing devices 202. Access to thefront end system 204 may require authorization or user authentication.In addition, a device or user privilege level may govern access to thefront-end system 204 and any data exchanges between the front-end system204 and the computing devices 202. Access to the front-end system 204may be governed by a privilege level associated with a computing device202 or a privilege level or credential given to the computing device 202or a user of the computing device 202, for example, by a group ororganization administrator.

The front-end system 204 may perform authentication of a customer, auser or a device before granting access to the resources of the filemanagement and collaboration system 206. The authentication may be basedon credentials, such as username and password information, or accesstokens, among others. The front-end system 204 may provide services andinterfaces that permit or enable user access. For example, the front-endsystem 204 may enable a web-based platform or a console-based platformthat provides information related to the services of the computingresource service provider 210 to the user. Further, the front-end system204 may enable the user to execute applications or tasks in thecomputing resource service provider 210, track and manage the executionof the applications or tasks and receive the results of the executionand transmit the results to user devices. As further described herein,the front-end system 204 may be the gateway by which the user orassociated devices 202 may utilize the plurality of services provided bythe computing resource service provider 210.

The document management and collaboration system 206 may be a collectionof computing devices and other resources collectively configured toenable and manage the execution and processing of documents forcollaboration between one or more users in a distributed system. Thedocument management and collaboration system 206 may, for example,enable uploading documents to the computing resource service provider210 and retaining and modifying metadata associated with the documents.The document management and collaboration system 206 may further allowfor search functions associated with the documents or their metadata aswell as collaborations between users on the documents.

Although the term “document” is used herein to describe objects producedor collaborated on by users of the computing resource service provider206, the term “document” is not limited to media, such as audio-visualmedia. A document may be computer files that are capable of beingproduced by or edited or viewed using a productivity program or suite.Accordingly, the document may be editable or non-editable text, images,drawings and websites, among others.

The content distribution edge network 212 of the computing resourceservice provider 210 may be a collection of computing devices and otherresources collectively configured to deliver content, such as webcontent, to a plurality of users. The content distribution edge network212 may have a plurality of edge locations, for example, that aredistributed in world-wide locations that are strategically placed tooptimize user data throughput and minimize latency. The contentdistribution edge network 212 may receive requests for content anddeliver the requested content to users. The content distribution edgenetwork 212 may interface with a storage service that stores a portionor all of the content and may cause the content to be retrieved andprovided to a requesting party. The content distribution edge network212 may be utilized to enable user-accessible websites or webapplications of the front-end system 204.

The object-level data storage service 214 may be a collection ofcomputing resources configured to synchronously process requests tostore and/or access data. The object-level data storage service 214 mayoperate using computing resources (e.g., databases) that enable theobject-level data storage service 214 to locate and retrieve dataquickly, so as to allow data to be provided in responses to requests forthe data. For example, the object-level data storage service 214 maymaintain stored data in a manner such that, when a request for a dataobject is retrieved, the data object can be provided (or streaming ofthe data object can be initiated) in a response to the request. Asnoted, data stored in the object-level data storage service 214 may beorganized into data objects. The data objects may have arbitrary sizesexcept, perhaps, for certain constraints on size. Thus, the object-leveldata storage service 214 may store numerous data objects of varyingsizes. As described herein, the object-level data storage service 214may store any type of document, such as a document source file, a commonrepresentation underlay, a preview, a thumbnail or extracted documenttext, among others.

The virtual computing service 216 may be a collection of computingresources configured to instantiate virtual machine instances on behalfof an entity of the computing resource service provider 210 (such as thedocument management and collaboration system 206) or on behalf of acustomer. A party may interact with the virtual computing service 216(via appropriately configured and authenticated API calls) to provisionand operate virtual computer systems that are instantiated on physicalcomputing devices hosted and operated by the virtual computing service216. The virtual computer systems may be used for various purposes, suchas to operate as servers supporting a website, to operate businessapplications or, generally, to serve as computing power. Further, thevirtual computer systems may be used to support database applications,electronic commerce applications, business applications and/or otherapplications. Although the virtual computing service 216 is shown inFIG. 2, any other computer system or computer system service may beutilized, such as a computer system or computer system service that doesnot employ virtualization or instantiation and instead provisionscomputing resources on dedicated or shared computers/servers and/orother physical devices.

The task management and workflow service 218 may be a collection ofcomputing devices and other resources collectively configured to performtask coordination and management services that enable executingcomputing tasks across a plurality of computing environments andplatforms. The task management and workflow service 218 tracks theprogress of workflow execution and performs the dispatching and holdingof tasks. Further, the task management and workflow service 218 maycontrol the assignment of hosts or physical or virtual computingmachines used for executing the tasks. A user may define a workflow forexecution, whereby the workflow may include one or more tasks. Theworkflow may be defined using an application programming interface (API)configured function call to the task management and workflow service218. Further, the user may specify task order for the workflow,conditional flows and timeout periods for restarting or terminating theexecution of the workflow. In addition, execution loops for the workflowmay be defined. As described herein, workflow execution may byasynchronous and may be preceded by synchronous execution of databasewrites.

The managed directory service 222 may be a collection of computingdevices and other resources collectively configured to serve as adirectory that enables users to log on to computing resources of thecomputing resource service provider 210 using one set of credentials andto enable administrators to uniformly apply security policies to thecomputing resource service provider 210. The managed directory service222 may enable a web-based console for user and group management and maybe used as an authentication system for user credentials.

The custom search service 224 may be a collection of computing devicesand other resources collectively configured to permit customizedsearches of data sets and enable establishing security or authenticationrequirements on a party performing a search. Further, the custom searchservice 224 allows for data set replication to enable consistentperformance in the case of outages. As described herein, the customersearch service 224 may be utilized for maintaining a search index ofcustomer documents and their associated metadata. Further, to ensureconsistent performance the searchable metadata or customer documents maybe replicated to ensure consistent performance and guard againstoutages.

The scalable database service 226 may be a collection of computingdevices and other resources collectively configured to provide astructured storage system that facilitates the storage and retrieval ofdocuments or data. The scalable database service 226 may benon-relational and may be based on a key-value model. Examples of thescalable database service 226 include a NoSQL database (for example, tobe distinguished from a relational structured query language (SQL)database). The scalable database service 226 may be used to storemetadata associated with documents, users and organizations. Inaddition, scalable database service 226 may store access privileges forusers of an organization.

In the environment illustrated in FIG. 2, a notification service 228 isincluded. The notification service 228 may comprise a collection ofcomputing resources collectively configured to provide a web service orother interface and browser-based management console. The managementconsole can be used to configure topics for which customers seek tonotify applications (or people), subscribe clients to the topics,publish messages, or configure delivery of the messages over clients'protocol of choice (i.e., hypertext transfer protocol (HTTP), e-mail andshort message service (SMS), among others). The notification service 228may provide notifications to clients using a “push” mechanism withoutthe need to periodically check or “poll” for new information andupdates.

FIG. 3 shows the functional entities of the front-end system and thedocument management and collaboration system in accordance with at leastone embodiment. The front-end system 304 includes a web server 332, anapplication service 334, a management console 336 and a control planeservice 338. The web server 332 may enable the execution of a web site,a single-page web application or a single-page interface that permits auser to transmit or upload documents to the document management andcollaboration system 306 and manage the documents. The web server mayfurther enable the user to view and edit documents, and providecommentary or feedback on the documents. The web server 332 may alsoenable an administrator or a user to set permissions or share modes thatspecify the privileges given to a user in accessing documents, forexample, using an access control policy. In addition, the web server mayenable users or devices to submit authentication credentials. Thecontent distribution edge network, described with reference to numeral212 in FIG. 2, may be used to distribute content of the web server 332.The actions performed by the user may be done via a website, anapplication or a management console and the web server 332 may enableexecuting the website, application or management console. Although oneweb server 332 is described with reference to FIG. 3, it may becontemplated that multiple web servers of any type may be used, wherebya portion of the web servers may be redundant.

The application service 334 may be a collection of computing devices andother resources collectively configured to serve as a user-exposedservice that receives requests from the user and services the requests.A user request may be made using a website or a management consoleaccessible to the user or a client that is executed on a user's devicemay make service requests on behalf of the user. The request may be anAPI function call and the application service 334 may process therequest and manage its execution. The application service 334 may alsobe responsible for receiving user credentials and request authenticationof the user from an authentication service. To cause the performance ofoperations requested by the user, the application service 334 may makeone or more function calls to services or entities of the computingresource service provider 210. For example, the application service 334may request user or access token validation from the managed directoryservice 222 or may cause search indices maintained by the customersearch service 224 to be updated.

The management console 336 may be a collection of computing devices andother resources collectively configured to permit organizations,administrators and users to register for utilizing document managementand collaboration services. The management console 336 may be used inaddition or as an alternative to a website or an application running ona user device and may permit users and administrators to make servicerequests using appropriately configured API function calls. For example,the management console 336 may be used for inviting a user to join adocument collaboration system and view and collaborate on documents.Further, the management console 336 may be used for allowing dashboardaccess, audit log access, permission setting (for example, foradministrators and user), storage limit setting (for example, fororganizations and users) and security setting (for example, password andencryption).

The control plane service 338 of the front-end system 304 may be acollection of computing devices and other resources collectivelyconfigured to serve as an interface that enables creating new computinginstances for document collaboration and management. Instances may becreated by transparently creating a directory in the managed directoryservice 222 or associating an existing directory (for example,maintained by the managed directory service 222 or by a user oradministrators) for document management and collaboration. The controlplane service 338 may be utilized to create a document directory and thedocument directory may be executed and served by the managed directoryservice 222. The document directory may be associated with anorganization having an administrator that is capable of providingpermissions and privileges to users. Following the creation of thedirectory, the application service 334 may be used to enable functionsaffecting folders or documents of the directory.

The document management and collaboration system 306 includes a searchservice 342, a directory service authorization interface 344, an accesscontrol entity 356 and a recommendation engine 358. The search service342 may be a collection of computing devices and other resourcescollectively configured to cause an uploaded document to becomesearchable. For example, the search service 342 may facilitate textextraction for a document, whereby the extracted text may be used toconstruct a character map for the document as described herein. Thedirectory service authorization interface 344 enables the documentmanagement and collaboration system 306 to delegate user authenticationto another entity such the managed directory service described withreference to numeral 222 in FIG. 2. The document management andcollaboration system 306 may submit user access tokens to theauthenticating party via the directory service authorization interface344 and may receive a response indicating whether a user may beauthenticated. As described herein, the access control entity 346 may bea collection of computing devices and other resources collectivelyconfigured to control user access to one or more documents retained bythe document management and collaboration system 306. The access controlentity 346 may evaluate an enforced access control policy and determinewhether one or more requested actions may be authorized. Further, theaccess control entity 346 may receive one or more recommendationsregarding access granted to one or more users and may determine whetherthe recommendations may be enforced based at least in part on a receivedaccess control policy.

FIG. 4 shows an example of directory structure in accordance with atleast one embodiment. A directory 402 may be maintained by a manageddirectory service and may be associated with an organization, which may,in turn, have one or more directories 402. The directory 402 includesone or more folders 404 (singularly referred to herein as folder 402).Further, a folder 404 may include one or more subfolders 406 that arenested within the folder 404. As may be recognized, a subfolder 406 mayfurther include one or more nested subfolders. A folder 404 may be afile structure within the directory 402 and, in some embodiments, thesecurity or permission privileges associated with the folder 404 mayapply to documents 408 within the folder 408 or subfolders 406 that arenested within the folder 404.

A folder 404 may retain one or more documents 408 (singularly referredto herein as document 408). As described with reference to FIG. 4, adocument may include a plurality of document versions 410. A documentversion 410 may be one revision of a document 408 or a subsequentversion or revision of an existing document including, for example, usermodifications and changes. Further, the permission or securityprivileges provided with respect to a document may apply to theplurality of document versions 410 associated with the document 408.Each document version 410 may have a plurality of representationsincluding a native document, an underlay and an overlay. The nativedocument may be an originally uploaded document (for example, in a fileformat compatible with a productivity suite). An underlay may be aportable representation of the native document that may be rendered on auser device utilizing a web application or a document management andcollaboration application. In addition, an overlay may be arepresentation of annotations made by users and collaborators. Forexample, an overlay may include a representation of highlights or textcommentary.

It is noted that more than one document versions 410 may include theoriginally uploaded document as the native document. Although asdescribed with reference to FIG. 4, a document 408 includes a pluralityof versions 410, whereby each version 410 may include a plurality ofrepresentations, as used in various contexts herein, a document may beany one of the versions or any one of the representations. For example,as used herein a user uploaded document may be the native document andan annotation document may be the overlay. The organization structureshown in FIG. 4 may be rendered in various styles or formats on a userdevice utilizing a web application or a document management andcollaboration application.

FIG. 5 shows an example of a document management and collaborationsystem in accordance with at least one embodiment. The documentmanagement and collaboration system 506 includes an access controlentity 508 and a recommendation engine 510. The access control entity508 manages access to one or more documents, folders or directoriesretained by the document management and collaboration system 506. Theaccess control entity 508 also enforces access control policies that areestablished by administrators or users of the document management andcollaboration system 506. The access control entity 508 may receive anaccess control policy from an administrator operating an administratordevice 502 and may utilize the policy to control user access todocuments, folders or directories maintained by the document managementand collaboration system 506. As described herein, an administrator ofan organization may have an authority to specify privileges for accessto an organization directory, folders or subfolders within the directoryor documents within a folder, subfolder or directory. It is noted thatthe administrator may manage more than directory of the documentmanagement and collaboration system 506. For example, the administratormay specify the users that may have access to a directory or itscontents and the privileges of the users to share the directory or itscontents with other users.

An access control policy may specify whether the user is permitted toshare a document with one or more users that are registered as beingpart of the organization or one or more users that belong to a domainname (for example, based at least in part on the user's email address).Further, the access control policy may specify that a user is permittedto share a document with any user, such as a user that is not registeredwith the document management and collaboration system 506. As describedherein, sharing a document may include sharing a folder or a subfolderof documents or sharing any group of documents. Further, if the documentsharing is permitted by the policy, a user may be able to view thedocument and collaborate on the document by providing comments andfeedback, among others.

The recommendation engine 510 may be used to provide recommendationsregarding access privileges afforded to users. The access privileges mayhave varying level and may include a permission to view, modify orannotate a document, among others. A recommended access privilege may berequired to confirmed or accepted by an organization administratorbefore being enforceable. In addition, an access control policy of anadministrator may specify that recommended access privileges may beenforced without prior acknowledgement from an organizationadministrator.

A user may seek to permit one or more other users access to one or moredocuments maintained by the document management and collaboration system506. The access may entail that the one or more other users view the oneor more documents and be able to comment on the one or more documents ormodify the one or more documents. In some embodiments, the one or moreusers for which access is sought may be anonymous users, whereby theaccess control entity 508 may not retain information associated with theone or more users. For example, if the users are anonymous, the usersmay not have an account with the document management and collaborationsystem 506, and, accordingly, the access control entity 508 may not beable to identify the users as being members of an organization or agroup.

A user may share a document with an anonymous user by, for example,causing a uniform resource locator (URL) associated with the document tobe provided to the anonymous user. The anonymous user may, in turn, usethe URL to access the document. As described herein, an access controlpolicy may specify whether a user or a group of users is permitted toshare a document or a group of documents with an anonymous user. Ifpermitted, the anonymous user may be able to view and comment on thedocument but, for example, may not be able to upload documents to thedocument management and collaboration system 506 due to the fact thatthe anonymous user is not registered as a user of the documentmanagement and collaboration system. Upon receiving a request for accessby the user, the document management and collaboration system 506 mayenable the user to register with the document management andcollaboration system 506. If anonymous sharing is not permitted by theaccess control policy, an anonymous user may not be able to access ashared document. Further, the document management and collaborationsystem 506 may not be used for sending an identifier of the document tothe anonymous user, such as a URL link to the document. As describedherein, sharing documents with anonymous users may facilitate viralsharing, whereby a member of an organization may share a document withone or more parties that are not registered users of the documentmanagement and collaboration system 506.

One or more users of the document management and collaboration system506 may have a federated identity that may be used to collectivelyenforce an access control policy. The federated identity may be based atleast in part on a domain name of an identity of the one or more users.For instance, users that are part of a domain name, such as example.com,may be part of a federated identity based at least in part on an emailaddress of the users, such as user1@example.com and user2@example.com.An administrator may specify collective policies for users having afederated identity. As described here, the policies may specifyprivileges given to members of a federated identity when an organizationmember shares one or more documents with the members of the federatedidentity. For example, the policy may specify that documents may beshared with members of a specified federated identity but may not beshared with anonymous users that are not members of a federatedidentity.

FIG. 6 shows an example of a method for evaluating an access requestbased at least in part on a requester's identity in accordance with atleast one embodiment. In the process 600, an access control entity, suchas access control entity 508 described with reference to FIG. 3,receives 602 a request from a user to access a document. As describedherein, the request may enable the user to view the document or commenton the document, among others. Further, in alternative embodiments, therequest may enable user access to a group of documents. The user may notbe registered with a document management and collaboration system or maynot be a member of an organization that utilizes the resources providedby the document management and collaboration system. Accordingly, thedocument management and collaboration system may not retain informationindicating whether the particular user has access privileges.

The access control entity determines 604 if the user is part of afederated identity. For example, the access control entity may evaluatethe request to obtain an identity associated with the user, such as anemail address, and may determine whether the user's identity is part ofa federated identity for a group of users or potential users that mayrequest access to one or more documents. The access control entityevaluates 606 an access control policy associated with the document. Theaccess control policy may specify restrictions that are to be enforcedfor controlling access to the document. The access control policy mayspecify, among others, one or more federated identities for groups ofusers that may be permitted or denied access to the document.

The access control entity determines 608 whether to permit the useraccess to the document based at least in part on the federated identityof the user. As described herein, the user may belong to a domain namethat is granted access to the document by the access control policy. Ifthe access control entity determines that the user it to be permittedaccess based at least in part on the user's federated identity, theaccess control entity permits 610 access to the document based at leastin part on the user's federated identity. After access is permitted, theuser may, for example, annotate or provide feedback on the document. Ifa negative determination is made, the access control entity does not 612permit access to the document.

Determining whether a user is associated with a federated identity mayinclude authenticating a user's credentials to verify that the user isassociated with the federated identity. When the federated identity is adomain name, the user may be required to log in to the documentmanagement and collaboration system using an email address that is partof the domain name. Further, the user may be authenticated by sending alink to the email address and requiring the user to follow the link inorder to complete the authentication process.

The access control policy may further specify whether access to adocument may be granted based at least in part on system-generatedsuggestions or recommendations. As described herein, the documentmanagement and collaboration system may generate one or more suggestionsregarding access granted to users. The suggestions may be counter or inconflict with elements of the existing policy, whereby, for example, asuggestion may call for permitting user access to a document that is notspecified in the policy. Accordingly, the policy may specify whether asuggestion that is counter to an existing policy may be enforceable. Asdescribed herein, the system-generated suggestions or recommendationsaccess grants may be based at least in part on one or more patternsassociated with users or document or one or more attributes associatedwith users or documents.

FIG. 7 shows an environment for providing document sharing suggestionsin accordance with at least one embodiment. In the environment 700, adocument sharing recommendation engine 710 may generate one or moresuggestions for user sharing privileges and provide the one or moresuggestions to an access control entity 708. The access control entity708 may retain an access control policy, for example, that is specifiedby an administrator, and may determine based at least in part on theaccess control policy whether a suggestion provided by document sharingrecommendation engine 710 may affect access to one or more documents byusers.

The document sharing recommendation engine 710 may be in communicationwith a variety of services and engines and may use information providedby one or more services or engines to generate suggestions regardingdocument sharing. As shown in FIG. 7, the document sharingrecommendation engine 710 may communicate with a cluster matching engine712, an email service 714, a calendar service 716, a location service718 and one or more other services and engines 720. The cluster matchingengine 712 may be a collection of computing devices and other resourcescollectively configured to construct a weighted cluster of keywords,phrases, strings or any type of characters utilized by a user. Thecluster may be constructed based at least in part on one or moredocuments that the user accessed (for example, by viewing, annotating oruploading, among others). As described herein, text or characters ofdocuments may be stored in an object-level data storage service, suchthe object-level data storage service described with reference tonumeral 226 in FIG. 2. The cluster matching engine 712 may access theobject-level data storage service to obtain the text of documentsassociated with a user. The cluster matching engine 712 may thenconstruct a weighted cluster for the user that associates one or morecharacters with a weight, whereby the weight may be a function of thefrequency of occurrence of the string of characters in documents relatedto the user. For example, the weight may be proportional (for example,linearly or non-linearly) to the frequency of occurrence of the stringsof characters in documents related to the user.

When a document is received by the document management and collaborationsystem, the cluster matching engine 712 may construct a cluster (alsoknown as a word cloud) for the document. The cluster matching engine 712may then identify one or more users whose access behavior correlateswith the received document. For example, the one or more users mayaccess or upload similar documents. To identify the one or more users,the cluster matching engine 712 may correlate the cluster of thereceived document with clusters of one or more users and provide theresults (such as a similarity measure) to the document sharingrecommendation engine 710 for use in making access recommendations. Whenconstructing a cluster or when correlating two or more clusters, commonwords or phrases, such as, “and”, “the” or “network”, may be assignedlesser weight than less common phrases, such as “cluster matching” or“access control policy”. Accordingly, the similarity measure between adocument and a user may be more heavily weighted by an overlap in lesscommon phrases than more common phrases.

In addition to receiving one or more similarity measures from thecluster matching engine 712, the document sharing recommendation engine710 receives information related to a link or a relationship between twoor more users or between a user and a document from an email service714. For example, the document sharing recommendation engine 710 mayreceive information indicating a document uploaded by a user wasreferenced in an email to another user. Accordingly, the indication maysuggest that it may be advantageous for the document to be shared withthe other user.

In addition, the document sharing recommendation engine 710 may receiveindications of a link between users or users and documents from acalendar service 716 or a location service 718. For example, thecalendar service 716 may notify the document sharing recommendationengine 710 if a user that submitted a document to the documentmanagement and collaboration system is scheduled for a meeting with oneor more other users. The document sharing recommendation engine 710 mayutilize the notification to indicate to the access control entity 708that the document may be shared with the one or more other users for theduration of the meeting. In addition, information received from thelocation service 718 may be used to alter the suggestion. For example,if the document sharing recommendation engine 710 receives an indicationfrom the location service 718 that a party to the meeting is not inattendance based at least in part on the party's location, the documentsharing recommendation engine 710 may alter the suggestion based atleast in part on the received indication. For example, the documentsharing recommendation engine 710 may not recommend that the document beshared with the party.

In addition, the document sharing recommendation engine 710 may receiveattributes associated with one or more users. The attributes may, forexample, specify whether the user is a subject matter expert in acertain area. The user may be tagged as a subject matter expert by anadministrator or other users (for example, using peer recommendation).Further, the user may be self-designated as a subject matter expert. Auser that is a subject matter expert may be provided with accessprivileges to access or review documents. The expertise of the user maybe evaluated in conjunction with a character cluster for a document todetermine whether the subject matter expertise of the user qualifies theuser as a reviewer of the document. Further, a user may request to begiven access privileges for a document in order to access the documentfor review.

The document sharing recommendation engine 710 may utilize one or moreindications received from the engines and service 712-720 to providedocument sharing suggestions to the access control entity 708. The oneor more indications may factor in varying level to a generatedsuggestion. For example, the document sharing recommendation engine 710may weight a similarity measure received from the cluster matchingengine 712 more heavily in generating a sharing recommendation than anindication of a link received from the calendar service 716.

As described herein, document sharing suggestions may be incorporatedinto an access policy of an organization and enforced for providingaccess to users. In alternative embodiments, the suggestion may only beprovided to an administrator of an organization and the administrator orthe organization may determine whether to incorporate the suggestions intheir policy. For example, in some embodiments, it may be not desirablefor an adaptive mechanism for providing access to be used as the basisfor providing access to documents. In the cases where sensitivedocuments (for example, private documents) are shared, the suggestionsmay be desired be sought to be confirmed by an administrator prior tobeing enforced as part of an access control policy.

Document sharing suggestions may also be based at least in part on userbehavior or user interaction with the document management andcollaboration system. For example, the document management andcollaboration system may receive a document from a user, whereby thedocument may be shared with a set of users. If, within a specifiedperiod of time, the user sends a second document to the documentmanagement and collaboration system, it may be suggested that the seconddocument be shared with the same set of users. The recommendation may bereinforced if the two documents have similar content as determined by,for example, a similarity measure.

FIG. 8 shows an example of a method for generating a similarity measurefor a document in accordance with at least one embodiment. In theprocess 800, a document management and collaboration system receives 802a document from a user. The document may be uploaded by a user that is amember of an organization and, upon being uploaded, may become part of agroup of documents for the organization. The document management andcollaboration system or an entity thereof, such as a cluster matchingengine, generates 804 a character cluster for the document. To generatethe character cluster, the cluster matching engine may analyze the textof the document to determine one or more characters, such as words orphrases, that are part of the document and associate each character ofthe one or more characters associated with a weight. The weight may bebased at least in part on the frequency with which the character occursin the document. Further, the weight may be based at least in part onhistorical data maintained by the document management and collaborationsystem. The historical data may specify the frequency with which acertain character has been observed to occur in documents, whereby ifthe character is observed more frequently in the received document thanspecified by the historical data, the weight associated with thecharacter in the cluster may be increased and vice-versa.

The cluster matching engine then calculates 806 a similarity measurebetween the generated cluster and one or more clusters that areassociated with one or more users. As described herein, a similaritymeasure may be a measure of significance or a measure of user affinityfor a document. For example, the similarity measure may be a distance,such as the Euclidean distance, in n-dimensional space between thegenerated cluster for the document and a generated cluster for a user.Further, the similarity measure may be a result of applying acorrelation function to one or more weights of the characters of thedocument and one or more weights of the characters of the user. When acorrelation function is used, the higher the correlation, the greaterthe similarity. The one or more users may not presently have access tothe document, and the similarity measure may be calculated in order todetermine whether the one or more users should be provided access to thedocument based at least in part on their interest in the content of thedocument. The similarity measure may be calculated by comparing thegenerated cluster of the document with character clusters of one or moreusers. For each user, the similarity measure may indicate user interestin the content of the document. After calculating the similaritymeasures, the cluster matching engine sends 808 the similarity measuresto a document sharing recommendation engine to be used for suggestingmodifications to an existing access control policy.

FIG. 9 shows an example of a method for recommending a change to accessprivileges in accordance with at least one embodiment. In the process900, a document sharing recommendation engine receives 902 one or moreuser or document attributes. The attributes may be received in order toprovide a recommend change to access privileges of a user. As describedherein, the attributes may be received from a cluster matching engine,an email service, a location service or a calendar service, amongothers. Further, the attributes may be used to calculate user affinityfor a document or a measure of significance of a document to a user,whereby the calculated affinity or measure may increase or decreasebased at least in part on the received attributes. The document sharingrecommendation engine then formulates 904 a suggestion for user accessprivileges based at least in part on the received attributes (or thecalculated affinity or measure). For example, the received attributesmay be used to suggest whether a user should be permitted access to adocument. Further, if the user is permitted access, a duration foraccess may be recommended, among others.

The document sharing recommendation engine then makes 906 the suggestedaccess privileges available to an organization administrator or a userand follows 908 an access control policy in determining whether toenforce the suggested access privileges. The administrator or the usermay be responsible for the document or for controlling access to thedocument. For example, the access control policy may specify that thesuggested access privileges are required to be accepted by theadministrator prior to be being enforced. Further, the access controlpolicy may specify that the suggested access privileges may be enforcedwith acceptance. Accordingly, the access privileges for a user may beset based at least in part on user activity in accessing the documentmanagement and collaboration system or services utilized by the user.

In some embodiments, the suggested access privileges may be madeavailable to an administrator or a user by including the suggestedaccess privileges in an email to the administrator or the user or bycausing a notification to appear in an application utilized by theadministrator or the user, whereby the application may be abrowser-based application or an independent application executed foraccessing or managing documents retained by the document management andcollaboration system. For example, the notification may be a popup thatappears in a side panel of the application. Further, the suggestedaccess privileges for user access to the document management andcollaboration system may be based at least in part on access privilegesthat are given to the user for accessing other services. For example, auser's privilege level for accessing the document management andcollaboration system may correspond to the user's privilege level foraccessing the email service or calendar service. A user that is alreadygranted a set of privileges for accessing services, such as the emailservice or calendar service, may be granted a minimum set of privilegesfor access documents retained by the document management andcollaboration system.

In some embodiments, the document sharing recommendation engine maycompare the suggested access privileges to access privileges specifiedin an existing policy (for example, a policy presenting enforced). Thecomparison may be performed in order to determine one or more changesthat may be made to the existing policy. The document sharingrecommendation engine may then provide the recommended change for theaccess privileges to an administrator. The administrator may specifywhether the policy should be modified in accordance with the recommendedchange. For example, the administrator may choose whether one or morerecommendation to be incorporated in the access control policy. In someembodiments, the administrator may specify (for example, using theaccess control policy) that all recommended changes are to beincorporated in the policy. In other embodiment, the access controlpolicy may specify that a recommended change is to be confirmed by theadministrator before it is enforced.

The access control entity of the document management and collaborationsystem may enable baselining of user access permissions. Baselining maybe performed to improve overall security of a document managementsystem. In one embodiment, a user that shared a document with anotheruser or expanded a permission associated with a document may be requiredto take action in order for the permissions to be kept in place.Baselining access permissions may also be performed for more than onedocument, such as groups, folders or collections of documents. If userdoes not take the proactive action, the permission may be reduced to aspecified level (for example, as specified in an access control policy.For example, the user may be requested to verify that the one or moreusers whose permission was expanded may continue to retain theirprivileges. An access control policy may specify when the baselining ofuser access permissions may be performed. For example, the accesscontrol policy may specify that a user be requested to confirm accessprivileges periodically or according to a time schedule. Further, thebaselining of user access permissions may be performed based at least inpart on user activity, among other factors. An administrator or anaccess policy may specify the trigger for performing baselining or setthe time schedule or period of time for performing baselining. Forexample, if a set time limit expires before a user accesses one or moredocument, the user's privilege for accessing the document may be reducedto specified level. An access control policy may specify whether auser's permission may be baselined automatically or whether anadministrator confirmation is required before the user's permission maybe reduced.

FIG. 10 illustrates aspects of an example environment 1000 forimplementing aspects in accordance with various embodiments. As will beappreciated, although a web-based environment is used for purposes ofexplanation, different environments may be used, as appropriate, toimplement various embodiments. The environment includes an electronicclient device 1002, which can include any appropriate device operable tosend and/or receive requests, messages or information over anappropriate network 1004 and, in some embodiments, convey informationback to a user of the device. Examples of such client devices includepersonal computers, cell phones, handheld messaging devices, laptopcomputers, tablet computers, set-top boxes, personal data assistants,embedded computer systems, electronic book readers and the like. Thenetwork can include any appropriate network, including an intranet, theInternet, a cellular network, a local area network, a satellite networkor any other such network and/or combination thereof. Components usedfor such a system can depend at least in part upon the type of networkand/or environment selected. Protocols and components for communicatingvia such a network are well known and will not be discussed herein indetail. Communication over the network can be enabled by wired orwireless connections and combinations thereof. In this example, thenetwork includes the Internet, as the environment includes a web server1006 for receiving requests and serving content in response thereto,although for other networks an alternative device serving a similarpurpose could be used as would be apparent to one of ordinary skill inthe art.

The illustrative environment includes at least one application server1008 and a data store 1010. It should be understood that there can beseveral application servers, layers or other elements, processes orcomponents, which may be chained or otherwise configured, which caninteract to perform tasks such as obtaining data from an appropriatedata store. Servers, as used herein, may be implemented in various ways,such as hardware devices or virtual computer systems. In some contexts,servers may refer to a programming module being executed on a computersystem. As used herein, unless otherwise stated or clear from context,the term “data store” refers to any device or combination of devicescapable of storing, accessing and retrieving data, which may include anycombination and number of data servers, databases, data storage devicesand data storage media, in any standard, distributed, virtual orclustered environment. The application server can include anyappropriate hardware, software and firmware for integrating with thedata store as needed to execute aspects of one or more applications forthe client device, handling some or all of the data access and businesslogic for an application. The application server may provide accesscontrol services in cooperation with the data store and is able togenerate content including, but not limited to, text, graphics, audio,video and/or other content usable to be provided to the user, which maybe served to the user by the web server in the form of HyperText MarkupLanguage (“HTML”), Extensible Markup Language (“XML”), JavaScript,Cascading Style Sheets (“CSS”) or another appropriate client-sidestructured language. Content transferred to a client device may beprocessed by the client device to provide the content in one or moreforms including, but not limited to, forms that are perceptible to theuser audibly, visually and/or through other senses including touch,taste, and/or smell. The handling of all requests and responses, as wellas the delivery of content between the client device 1002 and theapplication server 1008, can be handled by the web server using PHP:Hypertext Preprocessor (“PHP”), Python, Ruby, Perl, Java, HTML, XML oranother appropriate server-side structured language in this example. Itshould be understood that the web and application servers are notrequired and are merely example components, as structured code discussedherein can be executed on any appropriate device or host machine asdiscussed elsewhere herein. Further, operations described herein asbeing performed by a single device may, unless otherwise clear fromcontext, be performed collectively by multiple devices, which may form adistributed and/or virtual system.

The data store 1010 can include several separate data tables, databases,data documents, dynamic data storage schemes and/or other data storagemechanisms and media for storing data relating to a particular aspect ofthe present disclosure. For example, the data store illustrated mayinclude mechanisms for storing production data 1012 and user information1016, which can be used to serve content for the production side. Thedata store also is shown to include a mechanism for storing log data1014, which can be used for reporting, analysis or other such purposes.It should be understood that there can be many other aspects that mayneed to be stored in the data store, such as page image information andaccess rights information, which can be stored in any of the abovelisted mechanisms as appropriate or in additional mechanisms in the datastore 1010. The data store 1010 is operable, through logic associatedtherewith, to receive instructions from the application server 1008 andobtain, update or otherwise process data in response thereto. Theapplication server 1008 may provide static, dynamic or a combination ofstatic and dynamic data in response to the received instructions.Dynamic data, such as data used in web logs (blogs), shoppingapplications, news services and other such applications may be generatedby server-side structured languages as described herein or may beprovided by a content management system (“CMS”) operating on, or underthe control of, the application server. In one example, a user, througha device operated by the user, might submit a search request for acertain type of item. In this case, the data store might access the userinformation to verify the identity of the user and can access thecatalog detail information to obtain information about items of thattype. The information then can be returned to the user, such as in aresults listing on a web page that the user is able to view via abrowser on the user device 1002. Information for a particular item ofinterest can be viewed in a dedicated page or window of the browser. Itshould be noted, however, that embodiments of the present disclosure arenot necessarily limited to the context of web pages, but may be moregenerally applicable to processing requests in general, where therequests are not necessarily requests for content.

Each server typically will include an operating system that providesexecutable program instructions for the general administration andoperation of that server and typically will include a computer-readablestorage medium (e.g., a hard disk, random access memory, read onlymemory, etc.) storing instructions that, when executed by a processor ofthe server, allow the server to perform its intended functions. Suitableimplementations for the operating system and general functionality ofthe servers are known or commercially available and are readilyimplemented by persons having ordinary skill in the art, particularly inlight of the disclosure herein.

The environment, in one embodiment, is a distributed and/or virtualcomputing environment utilizing several computer systems and componentsthat are interconnected via communication links, using one or morecomputer networks or direct connections. However, it will be appreciatedby those of ordinary skill in the art that such a system could operateequally well in a system having fewer or a greater number of componentsthan are illustrated in FIG. 10. Thus, the depiction of the system 1000in FIG. 10 should be taken as being illustrative in nature and notlimiting to the scope of the disclosure.

The various embodiments further can be implemented in a wide variety ofoperating environments, which in some cases can include one or more usercomputers, computing devices or processing devices which can be used tooperate any of a number of applications. User or client devices caninclude any of a number of general purpose personal computers, such asdesktop, laptop or tablet computers running a standard operating system,as well as cellular, wireless and handheld devices running mobilesoftware and capable of supporting a number of networking and messagingprotocols. Such a system also can include a number of workstationsrunning any of a variety of commercially-available operating systems andother known applications for purposes such as development and databasemanagement. These devices also can include other electronic devices,such as dummy terminals, thin-clients, gaming systems and other devicescapable of communicating via a network. These devices also can includevirtual devices such as virtual machines, hypervisors and other virtualdevices capable of communicating via a network.

Various embodiments of the present disclosure utilize at least onenetwork that would be familiar to those skilled in the art forsupporting communications using any of a variety ofcommercially-available protocols, such as Transmission ControlProtocol/Internet Protocol (“TCP/IP”), User Datagram Protocol (“UDP”),protocols operating in various layers of the Open System Interconnection(“OSI”) model, File Transfer Protocol (“FTP”), Universal Plug and Play(“UpnP”), Network File System (“NFS”), Common Internet File System(“CIFS”) and AppleTalk. The network can be, for example, a local areanetwork, a wide-area network, a virtual private network, the Internet,an intranet, an extranet, a public switched telephone network, aninfrared network, a wireless network, a satellite network and anycombination thereof.

In embodiments utilizing a web server, the web server can run any of avariety of server or mid-tier applications, including Hypertext TransferProtocol (“HTTP”) servers, FTP servers, Common Gateway Interface (“CGI”)servers, data servers, Java servers, Apache servers and businessapplication servers. The server(s) also may be capable of executingprograms or scripts in response to requests from user devices, such asby executing one or more web applications that may be implemented as oneor more scripts or programs written in any programming language, such asJava®, C, C# or C++, or any scripting language, such as Ruby, PHP, Perl,Python or TCL, as well as combinations thereof. The server(s) may alsoinclude database servers, including without limitation thosecommercially available from Oracle®, Microsoft®, Sybase® and IBM® aswell as open-source servers such as MySQL, Postgres, SQLite, MongoDB,and any other server capable of storing, retrieving and accessingstructured or unstructured data. Database servers may includetable-based servers, document-based servers, unstructured servers,relational servers, non-relational servers or combinations of theseand/or other database servers.

The environment can include a variety of data stores and other memoryand storage media as discussed above. These can reside in a variety oflocations, such as on a storage medium local to (and/or resident in) oneor more of the computers or remote from any or all of the computersacross the network. In a particular set of embodiments, the informationmay reside in a storage-area network (“SAN”) familiar to those skilledin the art. Similarly, any necessary files for performing the functionsattributed to the computers, servers or other network devices may bestored locally and/or remotely, as appropriate. Where a system includescomputerized devices, each such device can include hardware elementsthat may be electrically coupled via a bus, the elements including, forexample, at least one central processing unit (“CPU” or “processor”), atleast one input device (e.g., a mouse, keyboard, controller, touchscreen or keypad) and at least one output device (e.g., a displaydevice, printer or speaker). Such a system may also include one or morestorage devices, such as disk drives, optical storage devices andsolid-state storage devices such as random access memory (“RAM”) orread-only memory (“ROM”), as well as removable media devices, memorycards, flash cards, etc.

Such devices also can include a computer-readable storage media reader,a communications device (e.g., a modem, a network card (wireless orwired), an infrared communication device, etc.) and working memory asdescribed above. The computer-readable storage media reader can beconnected with, or configured to receive, a computer-readable storagemedium, representing remote, local, fixed and/or removable storagedevices as well as storage media for temporarily and/or more permanentlycontaining, storing, transmitting and retrieving computer-readableinformation. The system and various devices also typically will includea number of software applications, modules, services or other elementslocated within at least one working memory device, including anoperating system and application programs, such as a client applicationor web browser. It should be appreciated that alternate embodiments mayhave numerous variations from that described above. For example,customized hardware might also be used and/or particular elements mightbe implemented in hardware, software (including portable software, suchas applets) or both. Further, connection to other computing devices suchas network input/output devices may be employed.

Storage media and computer readable media for containing code, orportions of code, can include any appropriate media known or used in theart, including storage media and communication media, such as, but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information such as computer readable instructions, data structures,program modules or other data, including RAM, ROM, Electrically ErasableProgrammable Read-Only Memory (“EEPROM”), flash memory or other memorytechnology, Compact Disc Read-Only Memory (“CD-ROM”), digital versatiledisk (DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices or any othermedium which can be used to store the desired information and which canbe accessed by the system device. Based on the disclosure and teachingsprovided herein, a person of ordinary skill in the art will appreciateother ways and/or methods to implement the various embodiments.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that various modifications and changes may be made thereuntowithout departing from the broader spirit and scope of the invention asset forth in the claims.

Other variations are within the spirit of the present disclosure. Thus,while the disclosed techniques are susceptible to various modificationsand alternative constructions, certain illustrated embodiments thereofare shown in the drawings and have been described above in detail. Itshould be understood, however, that there is no intention to limit theinvention to the specific form or forms disclosed, but on the contrary,the intention is to cover all modifications, alternative constructionsand equivalents falling within the spirit and scope of the invention, asdefined in the appended claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected,” when unmodified and referring to physical connections, isto be construed as partly or wholly contained within, attached to orjoined together, even if there is something intervening. Recitation ofranges of values herein are merely intended to serve as a shorthandmethod of referring individually to each separate value falling withinthe range, unless otherwise indicated herein and each separate value isincorporated into the specification as if it were individually recitedherein. The use of the term “set” (e.g., “a set of items”) or “subset”unless otherwise noted or contradicted by context, is to be construed asa nonempty collection comprising one or more members. Further, unlessotherwise noted or contradicted by context, the term “subset” of acorresponding set does not necessarily denote a proper subset of thecorresponding set, but the subset and the corresponding set may beequal.

Conjunctive language, such as phrases of the form “at least one of A, B,and C,” or “at least one of A, B and C,” unless specifically statedotherwise or otherwise clearly contradicted by context, is otherwiseunderstood with the context as used in general to present that an item,term, etc., may be either A or B or C, or any nonempty subset of the setof A and B and C. For instance, in the illustrative example of a sethaving three members, the conjunctive phrases “at least one of A, B, andC” and “at least one of A, B and C” refer to any of the following sets:{A}, {B}, {C}, {A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctivelanguage is not generally intended to imply that certain embodimentsrequire at least one of A, at least one of B and at least one of C eachto be present.

Operations of processes described herein can be performed in anysuitable order unless otherwise indicated herein or otherwise clearlycontradicted by context. Processes described herein (or variationsand/or combinations thereof) may be performed under the control of oneor more computer systems configured with executable instructions and maybe implemented as code (e.g., executable instructions, one or morecomputer programs or one or more applications) executing collectively onone or more processors, by hardware or combinations thereof. The codemay be stored on a computer-readable storage medium, for example, in theform of a computer program comprising a plurality of instructionsexecutable by one or more processors. The computer-readable storagemedium may be non-transitory.

The use of any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate embodiments ofthe invention and does not pose a limitation on the scope of theinvention unless otherwise claimed. No language in the specificationshould be construed as indicating any non-claimed element as essentialto the practice of the invention.

Preferred embodiments of this disclosure are described herein, includingthe best mode known to the inventors for carrying out the invention.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate and the inventors intend for embodiments of the presentdisclosure to be practiced otherwise than as specifically describedherein. Accordingly, the scope of the present disclosure includes allmodifications and equivalents of the subject matter recited in theclaims appended hereto as permitted by applicable law. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed by the scope of the present disclosure unlessotherwise indicated herein or otherwise clearly contradicted by context.

All references, including publications, patent applications and patents,cited herein are hereby incorporated by reference to the same extent asif each reference were individually and specifically indicated to beincorporated by reference and were set forth in its entirety herein.

What is claimed is:
 1. A computer-implemented method for controllingdocument access, comprising: under the control of one or more computersystems configured with executable instructions, receiving an attributeof a user of a document management and collaboration service provided bya computing resource service provider, the document management andcollaboration system being a system that maintains documents;determining an access control policy associated with at least onedocument maintained by the document management and collaboration serviceindicates that baselining is required for the at least one document;updating a user interface to request information to perform baseliningof a set of privileges associated with other users of the documentmanagement and collaboration service based at least in part on theattribute, the set of privileges defining access to the at least onedocument maintained by the document management and collaboration serviceby the other users; receiving a response from via the user interface;and setting the set of privileges of other users to a privilege levelspecified in the response.
 2. The computer-implemented method of claim1, wherein the computer-implemented method further comprises obtaininginformation indicating interactions of the user with a set of servicesprovided by the computing resource service provider of which thedocument management and collaboration service is a member.
 3. Thecomputer-implemented method of claim 1, wherein the attribute furthercomprises an indication that the user interacted with the least onedocument using computing resources of a particular service of the set ofservices.
 4. The computer-implemented method of claim 1, wherein theattribute further comprises a user affinity value for the at least onedocument, the user affinity value measuring significance of the documentto the user based at least in part on interactions with the at least onedocument performed by the user.
 5. A system, comprising: one or moreprocessors; and memory that includes instructions that, as a result ofexecution by the one or more processors, cause the system to: performbaselining on privileges associated with one or more users of a documentmanagement and collaboration system for accessing a particular document,the privileges enabling access to the particular document maintained bythe document management and collaboration system by at least:determining a set of privileges for a set of users of the one or moreusers for accessing the particular document; transmitting an approvalrequest of the set of privileges to a computing device associated with aparticular user, the particular user having privileges to approve accessto the particular document; receiving a response to the approvalrequest; and applying the set of privileges the particular document. 6.The system of claim 5, wherein the memory further includes instructionsthat, as a result of being executed by the one or more processors, causethe system to modify the set of privileges based at least in part on amodification to the set of privileges included in the response.
 7. Thesystem of claim 6, wherein performing baselining further comprisesdetermining the set of users based at least in part on a set ofattributes associated with the particular user.
 8. The system of claim7, wherein the set of attributes further comprises at least oneattribute indicating a significance measure between characters utilizedby the set of users and characters utilized by the particular user. 9.The system of claim 7, wherein the set of attributes further comprisesat least one attribute indicating an interaction of the particular userwith a service.
 10. The system of claim 9, wherein determining the setof users further comprises determining the set of users based at leastin part on an indication that the set of users interacted with theservice.
 11. The system of claim 5, wherein the memory further includesinstructions that, as a result of being executed by the one or moreprocessors, cause the system to receive, from an administratorassociated with the particular document, an indication that the set ofprivilege are not to be enforced.
 12. The system of claim 5, the memoryfurther includes instructions that, as a result of being executed by theone or more processors, cause the system to: receive, from a user deviceassociated with a first user of the set of users, a request to accessthe particular document; and provide the user device with access to theparticular document based at least in part on the set of privileges. 13.A non-transitory computer-readable storage medium having collectivelystored thereon executable instructions that, when executed by one ormore processors of a computer system, cause the computer system to atleast: receive an access control policy specifying whether to performbaselining on privileges of one or more users for accessing at least onedocument maintained by a document management and collaboration system,the privileges of the one or more users having been expanded by a firstuser; modify a user interface displayed to the first user to display arequest to baseline the privileges of the one or more users; and inresponse to the request, set the privileges of the one or more users toa privilege level specified by the first user through the userinterface.
 14. The non-transitory computer-readable storage medium ofclaim 13, wherein the instructions further comprise instructions that,when executed by the one or more processors, cause the computer systemto, on a condition that the first user does not specify the privilegelevel through the user interface, set the privileges of the one or moreusers to a second privilege level specified by the access controlpolicy.
 15. The non-transitory computer-readable storage medium of claim13, wherein the access control policy specifies that baselining theprivileges of the one or more users is to be performed periodically, dueto an occurrence of a trigger or according to a time schedule.
 16. Thenon-transitory computer-readable storage medium of claim 13, wherein theinstructions further comprise instructions that, when executed by theone or more processors, cause the computer system to identify at leastone user of the one or more users based at least in part on the at leastone user having an expanded privilege level from a privilege levelspecified in the access control policy.
 17. The non-transitorycomputer-readable storage medium of claim 13, wherein the instructionsfurther comprise instructions that, when executed by the one or moreprocessors, cause the computer system to identify at least one user ofthe one or more users due at least in part to an access interval of theat least one user to a document exceeding a threshold.
 18. Thenon-transitory computer-readable storage medium of claim 13, wherein theinstructions further comprise instructions that, when executed by theone or more processors, cause the computer system to: receive a requestto access a document from a user device operated by a user of the one ormore users; and evaluate the request based at least in part on theprivilege level specified by the first user through the user interface.19. The non-transitory computer-readable storage medium of claim 13, theprivilege level specified by the first user specifies that at least oneuser of the one or more users is permitted to view a document but notannotate the document, modify the document, or provide feedback on thedocument.
 20. The non-transitory computer-readable storage medium ofclaim 13, wherein the instructions further comprise instructions that,when executed by the one or more processors, cause the computer systemto modify the privilege level based at least in part on a secondprivilege level specific by an administrator associated with the firstuser.